NTISthis.com

Evidence Guide: UEEIC0014 - Develop, enter and verify programs in supervisory control and data acquisition systems

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

UEEIC0014 - Develop, enter and verify programs in supervisory control and data acquisition systems

What evidence can you provide to prove your understanding of each of the following citeria?

Hazards are identified, risks are assessed and control measures implemented

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Extent of SCADA system is determined from design brief and job specifications

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Process data is analysed for development of graphical design/mimic diagrams

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Programmable logic controller (PLC) analogue and digital addresses are related to tag databases

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Tag data types are entered and configured in tag database

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Graphic objects are created and added to a graphic library, as required, in accordance with vendor software

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Security requirements are determined for SCADA system to prevent access by unauthorised person/s

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

SCADA system is configured to provide appropriate reporting mechanisms

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Equipment, software and testing devices for work are obtained in accordance with workplace procedures and checked for correct operation and safety

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Develop and enter program using dedicated SCADA software

  1. WHS/OHS risk control measures and workplace procedures for carrying out the work are followed
WHS/OHS risk control measures and workplace procedures for carrying out the work are followed

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

SCADA software is used to develop human-machine interface (HMI) processes and to accept and implement operators control instructions

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Supervisory control functions, data acquisition components and automated tasks are programmed using SCADA software

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Data is manipulated within the SCADA software to function in accordance with design brief and job specifications

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Alarms and limits for processing variables are identified and programmed in accordance with workplace procedures

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Trends for process variables and limits are programmed in accordance with workplace procedures and manufacturer instructions

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Reports are configured to display/print appropriate information

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

User rights/security is configured to provide appropriate access to SCADA system

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Unplanned situations are responded to in accordance with workplace procedures and selected for safety and specified work outcomes

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Monitor verify and document programming activities

  1. Device operation is tested in accordance with WHS/OHS requirements and workplace procedures
Device operation is tested in accordance with WHS/OHS requirements and workplace procedures

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Entered objects and settings are tested in accordance with job specifications and manufacturer specifications

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

SCADA software tools are used to test and monitor programs, and operating anomalies are identified and corrected in accordance with workplace procedures

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

WHS/OHS work completion risk control measures and workplace procedures are followed

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

SCADA system specifications and programs are documented in accordance with workplace procedures

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Work completion is reported and relevant person/s notified in accordance with workplace procedures

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Required Skills and Knowledge

Evidence required to demonstrate competence in this unit must be relevant to and satisfy all of the requirements of the elements, performance criteria and range of conditions on at least two separate occasions and include:

analysing data

applying relevant work health and safety (WHS)/occupational health and safety (OHS) requirements, including implementing risk control measures

configuring user access rights

correcting programming faults and anomalies

creating graphic objects and adding to graphic’s library

dealing with unplanned events/situations in accordance with workplace procedures in a manner that minimises risk to personnel and equipment

developing and entering programs using dedicated supervisory control and data acquisition (SCADA) software

developing human-machine interfaces (HMIs)

developing SCADA system from design brief and job specifications

documenting SCADA system programming

entering tag data types into configured database

identifying programs for SCADA systems

monitoring, verifying and documenting programming activities

producing reports using SCADA

programming supervisory control functions and data acquisition components.

Evidence required to demonstrate competence in this unit must be relevant to and satisfy all of the requirements of the elements, performance criteria and range of conditions and include knowledge of:

SCADA system communications and networking, including:

programmable logic controller (PLC) interface requirements

networking requirements of the system

SCADA system differences from distributed control system (DCS) and process control systems

SCADA (HMI software package costing

types of networks available with SCADA HMI

coordinate and access of networking to factory network

the difference between SCADA and process control systems

mimics and animated graphics, including:

graphic designs, balance clarity of layout and navigation

assessment of data required to be entered in software package

validation of entered data

trending, including:

analysis of process to select data, including sampling of the process

viewing data and graphical representation of selected information

trend graphs and data matching

the difference between real time trends and historic trends

alarm logging, including:

analysing selected data and applying limits to processes

corrective actions and notifications of alarm status

alarm data availability for third-party software systems

recipes and scheduling, including:

methods of producing libraries for different process parameters required for varied production runs

analysis of different production runs, including amounts of materials, pressure, temperature and weights

alarm limits/material specifications

where and when scheduling is used

scheduling, setting limits and evoking program changes

data collection and databases, including:

produce a database of variable tags and range specifications involved in the process

conversion export of raw data into appropriate forms for data management and report creation, e.g., Excel and Paradox

types and layout of reports

aims of customer, management, statistical and account reports

analysis of data in reports: design and graphical data representations

assessment of data required for the report

programming language, including:

scripting languages in SCADA HMI software

automate tasks within the software PLC or SCADA

complex processing of process data where field equipment i.e. PLC does not have the capability or to minimise control lag

implementation and applications, including:

typical applications in manufacturing and process control, e.g., food processing, packaging, automotive industry, energy management and steel production and mining

relevant databases

relevant equipment, software and testing devices

relevant job safety assessments or risk mitigation processes, including risk control measures

relevant manufacturer specifications

relevant WHS/OHS legislated requirements

relevant workplace documentation and reporting

relevant workplace policies and procedures

SCADA system authorised user access and security requirements

SCADA systems programming

tag databases and PLCs.

Range Statement

Range is restricted to essential operating conditions and any other variables essential to the work environment.

Non-essential conditions may be found in the UEE Electrotechnology Training Package Companion Volume Implementation Guide.

Developing, entering and verifying programs in SCADA systems must include the following:

at least five graphic objects